[py] temporarily disable nightly TestPyPI publishing - #17920

• Remove Python from nightly release matrix to stop failing TestPyPI uploads.
• Add twine upload --verbose to production and nightly Python release targets.
• Preserve a one-line revert path by commenting out Python instead of deleting it.

graph TD
  NW["nightly.yml"] --> BW["bazel.yml workflow"] --> NPY["py:selenium-release-nightly"] --> TW["twine upload --verbose"] --> TPP{{"TestPyPI (disabled)"}}
  PR["py:selenium-release"] --> TW --> PYP{{"PyPI"}}

Loading

The following are alternative approaches to this PR:

1. Keep Python in matrix but ignore TestPyPI failures

• ➕ Nightly pipeline still exercises Python packaging end-to-end.
• ➖ Masks real publish failures and keeps generating noisy failures/alerts.
• ➖ May hide regressions until quota issue is resolved.

2. Conditional skip Python nightly only on schedule events

• ➕ Allows manual dispatch/callers to still run Python nightly when desired.
• ➖ More workflow logic and edge cases; still fails on schedule unless guarded correctly.

3. Publish Python nightly to GitHub Releases only (no TestPyPI)

• ➕ Keeps producing a consumable artifact without depending on TestPyPI availability.
• ➖ Changes distribution channel/consumer expectations; may require docs and tooling updates.

Recommendation: Current approach is the most practical mitigation: commenting out Python in the nightly matrix immediately stops the recurring failing publish while keeping a one-line revert once #17919 is resolved. Adding --verbose to both Twine upload invocations improves diagnosability without changing release semantics.

Bug fix (1) +2 / -0

BUILD.bazelAdd '--verbose' to Twine upload args for prod and nightly releases +2/-0

Add '--verbose' to Twine upload args for prod and nightly releases

• Updates the 'selenium-release' and 'selenium-release-nightly' Bazel 'py_binary' targets to pass '--verbose' to 'twine upload'. This ensures server response bodies are shown when uploads are rejected, improving failure diagnostics for both PyPI and TestPyPI.

py/BUILD.bazel

Other (1) +6 / -1

nightly.ymlComment out Python from nightly language matrix +6/-1

Comment out Python from nightly language matrix

• Replaces the inline language list with an explicit list and comments out the Python entry. This prevents Python nightly releases from running (and failing) while leaving an easy one-line revert once TestPyPI quota/issues are resolved.

.github/workflows/nightly.yml

Description

The new comment disabling Python nightlies (# - python) states what is disabled but not why,
leaving future maintainers without rationale or constraints. This reduces maintainability and
increases the chance the change is reverted incorrectly.

Code

.github/workflows/nightly.yml[R72-74]

+          - java
+          # - python
+          - ruby

Evidence

PR Compliance ID 4 requires comments to explain intent/rationale. The added comment # - python
only narrates the behavior (Python is commented out) without documenting why it was disabled (e.g.,
TestPyPI quota issue / refs #17919).

AGENTS.md: Comments Should Explain 'Why' Rather Than 'What'
.github/workflows/nightly.yml[71-76]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A new comment in the nightly language matrix disables Python (`# - python`) but does not explain the rationale.

## Issue Context
Compliance requires comments to explain *why* a non-obvious decision was made (e.g., TestPyPI quota failures / refs #17919) rather than merely describing *what* the code is doing.

## Fix Focus Areas
- .github/workflows/nightly.yml[72-74]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The Nightly workflow still allows selecting python via workflow_dispatch, but the
nightly-release matrix no longer includes python, so a manual run with language=python will
only execute echo skipping and publish nothing.

Code

.github/workflows/nightly.yml[R71-74]

+        language:
+          - java
+          # - python
+          - ruby

Evidence

The workflow’s manual dispatch input still includes python, but the job matrix was changed to
exclude it; the run expression then falls back to echo skipping when the selected language doesn’t
match any matrix entry.

.github/workflows/nightly.yml[6-18]
.github/workflows/nightly.yml[64-83]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The Nightly workflow still advertises `python` as a selectable `workflow_dispatch` input option, but the PR removes Python from the `nightly-release` job matrix. As a result, manually dispatching the workflow with `language=python` will not run any Python release command and will silently skip work.

## Issue Context
Python nightlies are intentionally disabled, but the workflow UI and inputs should reflect that to prevent confusing, successful-but-no-op runs.

## Fix Focus Areas
- .github/workflows/nightly.yml[6-18]
- .github/workflows/nightly.yml[64-83]

## Suggested changes
Choose one:
1) Remove `python` from `workflow_dispatch.inputs.language.options` while disabled.
2) Keep `python` selectable but add a guard in `prepare` (or before matrix execution) that fails with a clear error when `LANG == python` and Python is disabled.
3) Re-add Python to the matrix if manual Python nightlies should remain possible.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

💡 Did you know, you can route each action level your way: inline, summary, both, or drop

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗